Add an action for linting and releasing helm chart #364
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I've added a GitHub action that is linting helm chart on each pushed commit and releasing a new version helm chart automatically on each new push to the `master` branch. The linter job is checking whether the chart is changed, and in case it is, the linter expects the versions to be bumped. That means that all the changes to chart will be delivered to its users right away.
|
@allanger Let me think about what to do with it. But firstly, thanks for your contribution. |
|
We're off Travis and use an internal Action flow. But this just made me realize that the Travis Github app is still installed, getting triggered but doing nothing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I've added a GitHub action that is linting helm chart on each pushed commit and releasing a new version helm chart automatically on each new push to the
masterbranch.The linter job is checking whether the chart is changed, and in case it is, the linter expects the versions to be bumped. That means that all the changes to chart will be delivered to its users right away.
The releaser action is adding the helm chart archive to github releases and creating an index file in the branch that is used as a github pages branch (currently, hardcoded to gh-pages)
Since it's rather a worklfow change, I wouldn't expect you to actually merge it, cause you probably have you own workflow, and it's something new to maintain, but I think that many users of you chart would benefit from having an ability to get latest changes when they are merged to
masterinstead of waiting for the new release. So if you consider merging it I can support this action for a time beingThanks